Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1221

reference
459-tree-1
name
1221
tree-preservation-order

undefined

459-tpo-1
uprn
address-text
point
POINT (-1.024218 50.884533)
geometry
MULTIPOLYGON (((-1.024147 50.884526,-1.024150 50.884540,-1.024160 50.884552,-1.024176 50.884562,-1.024195 50.884569,-1.024217 50.884571,-1.024239 50.884569,-1.024259 50.884563,-1.024275 50.884553,-1.024285 50.884541,-1.024289 50.884527,-1.024286 50.884513,-1.024276 50.884500,-1.024261 50.884490,-1.024241 50.884484,-1.024219 50.884481,-1.024197 50.884483,-1.024177 50.884490,-1.024161 50.884499,-1.024151 50.884512,-1.024147 50.884526)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL